OASIS Errors
Page Last updated: 3 February 2008
Code |
Meaning |
Explanation |
2 |
File not found |
Does the file actually exist? Does the user have sufficent network rights to access the file? |
3 |
Path not found |
Directory does not exist. Possibly invalid directory entered in L3/F3. |
4 |
Out of file handles |
Increase FILES=nnn
in C:\CONFIG.SYS (MSDOS & Windows 9x) or C:\WINNT\SYSTEM32\CONFIG.NT (Windows NT/2000). |
5 |
Access denied |
File marked Read Only. Insufficient network rights to read or write to the file. Some other non-OASIS application has the file open. |
Further details of other more esoteric DOS error codes can be found in the Microsoft Knowledge Base article Q74463
Example:
Error DBFNTX 1003 open error
\oasis\foasis\01\fsubdis.x1 (DOS error 2)
called from DBSETINDEX(0)
called from NETUSEWL(214)
called from NETUSE(112)
called from F4F1 (3)
called from F4OASIS (487)
The traceback (the 'Called Froms') is useful in understanding the error message. The last entry is the starting point.
Module equivalences
Program |
Menu Option |
Description |
FOASIS |
D1 |
Purchases/Payments |
F2OASIS |
D2 |
Student Controls |
F3OASIS |
D3 |
Cash Register |
F4OASIS |
D4 |
Finance Reports/Setup |
F5OASIS |
D5 |
Fee Billing |
HOASIS |
F4 |
Standard Reports |
H1OASIS |
F5 |
OASIS Admin Extras |
H3OASIS |
G1 |
Finance Utilities |
IOASIS |
E1 |
School Information |
I6OASIS |
H5 |
Back to School |
LOASIS |
B1 or Enquiry |
Library Management |
L1OASIS |
F3 |
Library Extras |
L2OASIS |
B2 |
Library Circulation |
L4OASIS |
B3 |
Library Acquisitions |
L5OASIS |
B4 |
Library Reports/Utils |
L6OASIS |
B5 |
Library Periodicals |
LJOASIS |
H1 |
Rapid Retrospective |
MOASIS |
L2 |
System
Parameters |
ROASIS |
F1 or F2 |
Report Generator |
S2OASIS |
E3 |
Student Assesment |
SOASIS |
E2 |
Student and Staff |
TOASIS |
E4 |
Timetable |
T2OASIS |
E5 |
Timetable Management |
UOASIS |
I1 |
System
Check /V XXX |
CTR |
K3 |
CTR Utility |
ZOASIS |
L1 |
Update System |
Error code |
Description |
Meaning |
Possible Causes and solutions |
DBFNTX/1001 |
Open Error *.dbf |
Data file could not be opened |
Data file does not exist. Insufficient network rights to open. Another application has the file open exclusively. Insufficient file handles. |
DBFNTX/1003 |
Open Error Index |
Index file could not be opened |
Index file does not exist. Insufficient network rights to open. Insufficient file handles. |
DBFNTX/1004 |
Open error (Creating *.dbf) |
Could not create the file |
Insufficient disk space. Floppy disk with errors. Illegal filename - contains space, colon or backslash. Existing file is ReadOnly. Insufficient network rights to create the file. |
DBFNTX/1006 |
Open error (Creating index) |
See 1004 |
|
DBFNTX/1010 |
Read Error |
Error encountered while reading a file |
Floppy disk with errors. Network connect to server lost. Corrupt indexes causing a read beyond the end of a data file. |
DBFNTX/1011 |
Write error |
Error encountered while writing a file |
Insufficient disk space. Floppy disk with errors. File is ReadOnly. Insufficient network rights. |
DBFNTX/1012 |
Corruption detected |
The file is (or appears to be) corrupted |
Data
file. Is the
file really a dBase format file? Check for garbage by opening with DBU.
Replace the file with a good backup copy |
DBFNTX/1020 |
Data Type Error |
The value assigned to a field was of the wrong type. e.g. trying to store 'DOG' to a numeric field |
Usually a programming error. |
DBFNTX/1021 |
Data Width Error |
The value assigned to a numeric field variable could not be stored in the available field width. e.g. trying to store 999 into a field defined as N2 |
OASIS will produce this error on large Novell networks with more than 99 stations which causes the STATION NUMBER to be 3 digits long. Some Windows peer-to-peer networks produce the same error because they return a STATION NUMBER of 255. Otherwise it is generally a programming error. |
BASE/5300 |
Memory low. |
Not enough free conventional memory |
OASIS requires 530kb of free conventional memory for proper operation. On DOS computers, ensure HIMEM and EMM386 NOEMS are loaded and DOS=HIGH, DOS=UMB are present in CONFIG.SYS. |
BASE/???? |
|
|
Any other BASE error will almost always be due to a programing oversight of some kind. |
TERM/0 |
Printer not ready. |
|
Directly
connected printer; the printer is off-line or not connected. |
Internal Errors |
|
|
|
24 |
Write error |
Unable to write to a file |
The disk is full. A floppy disk has errors. Existing file is Read Only. Insufficient network rights to write to the file. |
416 |
Read error on Overlay file |
When the program went to page in another section of the program, it was unable to do so |
Lost connection to fileserver. Network problems. Insufficient file handles. |
1210 |
Data and Index files out of sync |
An index file does not match its data file |
Usually caused by an external program (such as DBU) modifying data without updating the index files. Otherwise, a programming error. Rebuild the index file. If that does not work, delete the index file and rebuild. |
5302,3,4,5,6 |
Conventional memory exhausted |
Not enough free conventional memory |
OASIS requires 530kb of free conventional memory for proper operation. On DOS computers, ensure HIMEM and EMM386 NOEMS are loaded and DOS=HIGH, DOS=UMB are present in CONFIG.SYS. |
5311 |
VMM Unable to create swap file |
The Virtual memory (VM) subsystem is unable to create a swap file on a disk |
The disk is full; the target directory is full; Insufficient file handles; invalid path specified in SWAPPATH, CLIPPER environment variable; insufficient network rights to create the file. |
5313 |
VMM Write error on swap file |
The Virtual memory (VM) subsystem is unable to write to its swapfile on disk |
The disk is full; Bad sectors encountered; swap file has been deleted by another application. Lost connection to fileserver. Network problems. |
Or for additional opinions try this link: HOLMES PAGE
Audio Beep Errors:
Number of Beeps |
Description of
Problem |
Solution |
1 beep |
DRAM refresh failure |
Try re-seating the memory first. If the error still occurs, replace the memory with known good chips. |
2 beeps |
Parity Circuit Failure |
|
3 beeps |
Base 64K RAM failure |
|
4 beeps |
System Timer Failure |
Send System Board in for Repair |
5 beeps |
Processor Failure |
|
6 beeps |
Keyboard Controller / Gate A20 Failure |
Try re-seating the keyboard controller chip. If the error still occurs, replace the keyboard chip. If the error persists, check parts of the system relating to the keyboard, e.g. try another keyboard, check to see if the system has a keyboard fuse. |
7 beeps |
Virtual Mode Exception Error |
Send System Board in for Repair |
8 beeps |
Display Memory Read/Write Failure |
Indicates a memory error on the video adapter. Try re-seating the video card. If it still beeps, try replacing the video card or the memory on the video card. |
9 beeps |
ROM BIOS Checksum Failure |
Indicates faulty BIOS chip(s). It is not likely that this error can be corrected by re-seating the chips. Consult the motherboard supplier or an AMI product distributor for replacement part(s). |
10 beeps |
CMOS Shutdown Register Read/Write Error |
Send System Board in for Repair |
1 long 2 short |
Video failure |
Reseat the video board - replace if board is determined to be faulty. |
1 long 3 short |
Video failure |
|
1 long |
POST passed. |
No Errors |
Error Messages/Codes
Error Message |
Problem |
Solution |
CH-2 Timer Error |
Non fatal. Could be caused by a peripheral. |
|
INTR #1 Error |
Interrupt Channel 1 has failed the POST test |
Check system boards for IRQs 0-7. |
INTR #2 Error |
Interrupt Channel 2 has failed the POST test |
Check system boards for IRQs 8-15. |
CMOS Battery State Low |
|
Replace battery. |
CMOS Checksum Failure |
A checksum is generated when CMOS values are saved for error checking on subsequent startups. This error message will appear if the checksum is different from one boot-up to the next. |
Run the setup program again to correct the problem. |
CMOS Memory Size Mismatch |
Usually caused when you add or remove memory from your system but could be caused by memory that has failed. |
Run setup. |
CMOS System Optons Not Set |
CMOS values are either corrupt or do not exist. |
Run Setup. |
Display Switch Not Proper |
Many motherboards have a jumper setting that allows you to specify whether you have a color or monochrome monitor. |
Correct the switch position. |
Keyboard is locked ... Unlock it |
|
Unlock the keyboard. |
Keyboard Error |
There is a problem with the keyboard |
Make sure your keyboard BIOS is compatible, that the keyboard is plugged in completely, and that no keys are stuck. Or, change the BIOS keyboard setting to "Not Installed" to skip the test. |
K/B Interface Error |
There is a problem with the keyboard connector on the motherboard. |
|
FDD Controller Failure |
The BIOS cannot communicate with the floppy drive controller. |
The floppy may be disabled, also check that the cable is not loose. |
HDD Controller Failure |
As above, but for hard disks. |
|
C: Drive Error |
The system cannot get a response from drive C. |
The hard disk type is most likely set incorrectly, or the disk may not be formatted or connected properly. |
D: Drive Error |
Same as above except for drive D. |
Same as above. |
C: Drive Failure |
The drive was detected but failed. More serious than error. |
|
D: Drive Failure |
Same as above. |
|
CMOS Time and Date Not Set |
|
Run Setup |
Cache Memory Bad, do Not Enable Cache! |
|
Cache may indeed be bad, if so replace. May simply need re-seating. |
8042 Gate-A20 Error! |
The Gate-A20 portion of the keyboard controller has failed. |
Replace the keyboard chip (8042) |
Address Line Short |
There is a problem with the memory address decoding circuitry. |
Try rebooting, (turn the system off and then on 10 seconds later). The problem may correct itself. |
DMA #1 Error |
There is an error in the first DMA channel on the motherboard |
Could be caused by a peripheral device. |
DMA Error |
There is an error within the DMA controller on the motherboard. |
|
No ROM Basic. |
There is nothing to boot from. (i.e.- the system cannot find an operating system). |
Be certain that a bootable disk is defined in the system setup. |
Diskette Boot Failure |
The diskette in the specified boot-up drive is corrupt. |
|
Invalid Boot Diskette |
Same as above, but the disk is readable. |
|
On Board Parity Error |
There is a parity error with memory on the motherboard at address XXXX (hex). (On Board specifies that the memory is not on an expansion board, but rather is located on the motherboard physically). |
Possibly correctable with software from the motherboard manufacturer. (also do a Virus Check - some viruses cause parity errors). |
Off Board Parity Error |
There is a parity error with memory installed in an expansion slot at address XXXX (hex) |
Same as above. |
Parity Error |
There is a parity error with memory somewhere in the system. |
Same as above. |
Memory Parity Error at XXXX |
Memory has failed. If it cannot be determined, it is displayed as XXXX, if not, as ???? |
Same as above. |
I/O Card Parity Error at XXXX |
Same as above. |
Same as above. |
DMA Bus Time-out |
A device has driven the bus signal for more than 7.8 microseconds. |
Troubleshoot all system boards. (remove them and try to isolate the failure) |
Memory mismatch, run Setup |
|
Disable Memory Relocation if possible. |
EISA CMOS Checksum Failure |
The checksom for EISA CMOS is bad, or the battery is bad. |
|
EISA CMOS Inoperational |
A read/write failure occured in extended CMOS RAM. |
The battery may be bad. |
Expansion Board not ready at Slot X |
AMI BIOS cannot find the expansion board in X slot. |
Verify that the board is in the correct slot and is seated properly. |
Fail-Safe Timer NMI Inoperational |
Devices that depend on the fail-safe NMI timer are not operating correctly. |
|
ID information mismatch for Slot X |
The ID of the EISA expansion board in slot X does not match the ID in CMOS RAM. |
|
Invalid Configuration Information for Slot X |
The configuration information for EISA board X is not correct. |
Run the ECU. |
Software Port NMI Inoperational |
The software port NMI is not working. |
|
BUS Timeout NMI at Slot X |
There was a bus timeout NMI at Slot X. |
|
(E)nable (D)isable Expansion Board? |
|
Type E to enable the board that had an NMI or D to disable it. |
Expansion Board disabled at Slot X |
The expansion board NMI was generated from slot X. |
|
Fail-Safe Timer NMI |
A fail-safe timer NMI has been generated. |
|
Software Port NMI |
A software port NMI has been generated. |
|